Architecture
How Thoth stays local-first.
These diagrams map the main systems behind Thoth: the agent orchestrator, context assembly, memory graph, workflows, channels, Designer Studio, safety boundaries, and self-management loops. The same principle runs through each layer: keep durable user data local, make external services opt-in, and give the user clear control over actions.
Conversations, memory, media, tasks, wiki vaults, and project assets live on the user's machine.
Ollama runs locally, while provider APIs, custom endpoints, and ChatGPT / Codex remain explicit choices.
Tool results, web pages, channel attachments, and remote MCP servers are treated as untrusted context.
Destructive tools, settings changes, workflow actions, and external delivery paths pass through guardrails.
Subsystem Maps
Open any diagram for a larger view. The gallery starts with the full core-agent map, then moves through the specialized subsystems that make Thoth useful day to day.
Core Agent
Interfaces, model routing, context, memory, tool calls, workflows, storage, and control planes.
Context Assembly
How current turns, history, skills, memories, documents, and tool results become model-ready context.
Memory System
Capture, extraction, graph storage, semantic retrieval, wiki export, and Dream Cycle refinement.
Background Workflows
Natural-language workflow creation, scheduling, execution, approvals, delivery, and recurring loops.
Multi-Channel Runtime
Messaging entry points, adapters, normalization, identity mapping, attachment handling, and delivery.
Designer Studio
Project modes, page generation, media, targeted edits, preview sandboxing, export, and publish paths.
Safety, Privacy & Control
Local-first boundaries, approvals, prompt-injection defense, tool permissions, credentials, and updates.
Self-Awareness
Status introspection, diagnostics, capability registry, insights, skill guidance, and controlled self-management.
Want the implementation detail?
The written architecture reference covers modules, storage layout, provider routing, update flow, packaging, and system boundaries.